An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello, I’m having a recurring TestFlight issue. This is already the third time it has happened. All of my TestFlight builds are automatically marked as Expired, and I’m unable to submit a new processed build for External Testing. App Store Connect returns: HTTP 422 ENTITY_UNPROCESSABLE.BETA_CONTRACT_MISSING Beta Contract is missing. My Developer Program membership and agreements are active, with no pending agreements. The issue happens directly in the App Store Connect website, with no third-party service involved. Has anyone else experienced this? It seems like a TestFlight backend / Beta Contract provisioning issue. I’ve already contacted Apple Support multiple times, but the problem keeps returning. Thanks.

Hello, Our new app TruckSOS (Apple ID: 6801003473) was submitted for review on August 15, 2026. On August 16 we received a Guideline 2.1 (Information Needed) request with seven items, including a screen recording of the app running on a physical device. On August 18 we replied in the Resolution Center with all seven requested items, including a full 11-minute screen recording captured on a physical iPhone running iOS 26.3.1 (account creation, login, core flows, UGC reporting and blocking, permission prompts, and account deletion). Since then there has been no response of any kind. Timeline: Aug 15: version 1.0 submitted (submission ID 7cc57105-24c7-4300-ab4d-73a47aa9e82f) Aug 16: Guideline 2.1 - Information Needed request Aug 18: full reply with all requested information and the screen recording attached Aug 25: polite follow-up in the same thread - no answer Expedited review request refused by the form with "You don't have a submission in review" (the submission is in "Unresolved Issues" status) Aug 26: accepted the updated Program License Agreement in case it was blocking anything - no change Aug 28: wrote to Developer Support - no reply yet It has now been 12 days since we provided everything that was requested and the review appears to be stalled. Is there anything else we should do, or could someone from the App Review team take a look? Thank you!

Hello, My app, Pellix, has been stuck in “Waiting for Review” for approximately 9 days, and the review process has still not started. I contacted Apple Developer Support 3 days ago, but I have not received any response yet. There are also no outstanding actions or messages in App Store Connect. Submission ID: 383b92d9-bc90-4be4-bd66-d0b8ecd53966 Case ID: 20000146897751 Could someone from the App Review team please confirm whether my submission is correctly queued for review or help escalate the existing support case? Thank you.

Hoping someone from App Review can take a look at a first submission that has been sitting in "In Review" since 22 July. App: NextUp (Apple ID 6758259427), iOS 1.2, build 30141 Submission ID: 5ea082d9-58b1-4430-b897-5111bc78225a Submitted: 22 July 2026 Status: In Review. All 11 items show In Review (app version, subscription group, 4 auto-renewable subscriptions, 5 consumables). What has happened so far: 22 July: automated metadata return for a missing Terms of Use link. Fixed it the same morning and resubmitted. The submission moved to In Review and has not changed since. 9 August: requested an expedited review. Accepted on screen, no follow-up. 19 August: opened case 20000141656520 asking for status. Reply on 24 August confirmed the expedite had been accepted and the app is In Review. No ETA, nothing asked of me. 30 August: followed up on the same case. Auto-acknowledged. There are no messages in Resolution Center after the resubmission and nothing waiting on me. The build is valid, the demo account in App Review Information works, all metadata links resolve, and the Paid Applications agreement, banking and tax are active. I understand the queue is long at the moment, but 39 days without a single reviewer note is well outside anything I have seen. Could someone check whether this submission is actually assigned, or whether something is holding it that I can't see from my side? Happy to provide anything that would help.

Hello Apple App Review Team, We are requesting assistance with our first submission of Local & Traveler – iOS 1.0.0, which has remained in Waiting for Review for more than 48 hours without entering In Review. We have already submitted an Expedited App Review Request and contacted Apple Developer Support regarding the review status. App: Local & Traveler Apple App ID: 6803864337 Version: 1.0.0 Current Status: Waiting for Review This delay is now directly affecting our coordinated commercial launch, including marketing activities, local onboarding, partner coordination, and operational rollout. Our pilot launch covers Paris, Barcelona and Rome, with additional cities planned afterwards. Could someone from the App Review team please check whether our submission is progressing normally and, if possible, help escalate it to the appropriate review team? We are ready to respond immediately to any additional information required. Thank you very much for your support

App Review Appeal Pending for More Than 10 Days — Is This Normal? Hi everyone, I’m looking for advice regarding an App Review appeal that has now been pending for more than 10 days without a decision or meaningful status update. Before submitting the appeal, our app had already been waiting for App Review for approximately 5 days. It was then reviewed and rejected, after which we submitted an appeal to the App Review Board. We understand that appeals may require additional investigation, but it has now been over 10 days since the appeal was submitted, and we still have no estimated timeline for a decision. This is significantly delaying our app release and making it difficult for us to plan updates and operations. Has anyone recently experienced a similar wait time with the App Review Board? Also, is there an official way to follow up or escalate an appeal when it has been pending for this long? We have already followed the normal appeal process and are simply trying to understand whether this timeframe is expected. Any recent experience or advice would be greatly appreciated. Thank you.

Hello Apple Developer Relations / App Review Team, My app, Pulse Circle, has been in “Waiting for Review” for over a week, and I have still not received any update. App Store link: https://apps.apple.com/in/app/pulse-circle/id6749582619 I have already tried the fast approval/expedited review process and have also sent an email regarding the delay, but I have not received any response or indication of when the review will begin. What is particularly frustrating is the lack of transparency around the process. Apple communicates that the vast majority of apps are reviewed within 24 hours, yet in practice the experience can vary dramatically. Sometimes an app is reviewed within an hour, while other times developers are left waiting for a week or even two weeks with no explanation. As developers, we understand that App Review takes time and that some apps may require additional review. The issue is that when an app remains in “Waiting for Review” for such a long period, there is no information explaining what is happening or when we can realistically expect a review. We also have marketing campaigns and launch plans scheduled around the App Store release. A completely unpredictable review timeline makes it extremely difficult for developers and businesses to plan. Apple charges developers an annual Apple Developer Program membership fee, so I would expect a more transparent and predictable process, especially when an app is simply waiting to enter review. There are also many developers discussing similar delays across developer forums, Reddit, and other communities. This makes it feel like the review timeline can be somewhat random. I am not asking for preferential treatment. I am simply asking for: An update on why this app has remained in Waiting for Review for over a week. Confirmation that the app is actually in the review queue. A realistic estimate of when the review is expected to begin. Better transparency for developers when review timelines significantly exceed the normal timeframe. Please review Pulse Circle and move it into the review process as soon as possible. Thank you.

Hi everyone, I’m a developer maintaining an existing app that has been live on the App Store for many years. We regularly submit updates, and normally our submissions are reviewed and approved within 48 hours without any issues. However, I’m currently experiencing an unusual situation and would appreciate some advice. 19 August: I submitted a new version of the app. It went into review but was rejected under: Guideline 1.1 - Safety - Objectionable Content The app’s marketing includes terms or images that reference objectionable content or services. These references can be found in the app’s metadata, including, but not limited to, the following metadata field(s): description and name. I’m not sure what triggered this rejection because the app name and description have not been changed for years. The app has been live and regularly reviewed during that time without this issue. The rejection also did not identify the specific wording or content in the app name or description that was considered objectionable. I responded to the review team explaining the situation and asked them to identify the specific part of the metadata that caused the issue so that we could review and update it if necessary. However, I did not receive any further response. I also submitted an appeal, but I have not received a response after several days. 21 August: Because we still need to maintain the app and release updates, I cancelled the previous submission and submitted a new version for review. However, this submission has also remained pending and has not moved forward to review. 25 August: I cancelled the submission again and created another submission containing both maintenance updates and a big launch for a new country. This update is important for our business because the new operation is scheduled to launch on 1 September. We need the app update to be reviewed and approved before then. I have also submitted an expedited review request and a new ticket, but it still hasn’t moved forward or been reviewed. My questions Is there anything I can do to get the current submission reviewed, given that the previous submission was rejected and the appeal has not received a response? Could the previous Guideline 1.1 rejection be causing the subsequent submissions to remain pending? Should I continue waiting for the current submission, or is there another recommended process for escalating this situation? The delay is now becoming critical because the new country launch is scheduled for 1 September, and not having the required app update available by then would significantly affect our business operations. Any advice from other developers who have experienced a similar situation would be greatly appreciated. Thank you.

Hello Apple Developer Relations / App Review Team, I’m hoping someone from Apple can please take a look at our App Review situation. Our app has been in the review/resubmission process since July 7, 2026, and today is August 30, 2026. We have now been waiting for almost two months overall. For the previous submission alone, we waited approximately 21 days before receiving the review result. We addressed the issues identified by App Review and have now submitted an updated version again. App Apple ID: 6789650549 We completely understand that review times can vary and that Apple needs sufficient time to properly review every submission. However, the delays we have experienced are far beyond the normal review timeframe and are having a significant impact on our launch. At this point, our main concern is no longer the review outcome itself, but the unusually long amount of time between each review cycle. We would sincerely appreciate it if someone from the App Review team could check the status of this app and, if possible, help get the latest submission reviewed as soon as possible. We have already spent a considerable amount of time making sure the app complies with the App Store Review Guidelines, and we are ready to immediately address any further issue if one is found. Thank you very much for your help.

Hello, My app sat in "Waiting for Review" with no status change for over nine days, and I would appreciate any guidance on whether my submission is properly queued. Details: App ID: 6759439888 App name: PLUed Submission type: new app (first submission), submitted together with a first in-app purchase Original submission: August 19, 2026 Resubmitted: August 29, 2026 with a new build (1.0, build 82), in case the original submission was stuck Current status: Waiting for Review, unchanged; the build has never moved to "In Review" at any point What I have already checked: Agreements, Tax, and Banking are current with no pending items Export compliance answered (ITSAppUsesNonExemptEncryption declared in the build) App Privacy and age rating questionnaires complete Review notes include full access instructions for the reviewer The in-app purchase is attached to the same review submission (both items show Waiting for Review) No rejection, no Resolution Center message, and no request for additional information at any point Contacted Apple Developer Support — case ID 20000148679022, awaiting response The app is part of a coordinated September 1 launch and is already live on other platforms, so I am trying to determine whether this is normal queue depth for a first submission or a submission that is stuck. Could someone confirm whether this submission is queued correctly? Thank you. Clay

Hello, I’m looking for some guidance regarding an App Store review that has been taking significantly longer than expected. Our app, SafeKnot, was originally submitted on August 20, 2026 at 20:24. Shortly after submission, we received an automated App Review message indicating two issues: The app uses Screen Time APIs and needed the Family Controls entitlement. The app offers auto-renewable subscriptions but the App Store metadata was missing a functional Terms of Use (EULA) link. We addressed both issues: The required Family Controls entitlement/configuration was completed. The Terms of Use information was added correctly. We then resubmitted the app for review. Since the resubmission, the app has remained in “In Review” status for several days, and we have not received any additional questions, rejection messages, or requests for information from App Review. We also contacted Apple Developer Program Support and received the following case number: Case ID: 20000149485605 Could an Apple engineer or App Review representative please advise whether the submission is still progressing normally, or whether there may be an issue preventing the review from proceeding? We do not want to cancel and resubmit the app unnecessarily, as it is already in the review process. Thank you very much for your help.

I have spent the last few months working on a new app, "Jelly Music — by JellyLabs", which is a music client for Apple Music users. It has 100+ TestFlight users who are using it daily and sharing great feedback. The app does not include any template code and is not overly similar to any existing apps on the App Store, as far as I know. It includes lots of unique features, like a personal dj (like Spotify), radio stations from playlists (with different station discovery modes), custom app themes, lots of view options for your playlists/songs/artists/albums, "bump song to top of library" option, Sonos speaker controls, Mac Bridge Sync which allows you to view/edit your song metadata from your iPhone/iPad while your Mac writes the changes to your library, etc. See video here: https://www.reddit.com/r/AppleMusic/comments/1vwkp0n/jelly_music_a_new_apple_music_client_with_full/ The app did previously include one third party open source dependency, FluidAudio (a voice model that powered a live dj feature), so my latest version removed that in case that was causing a binary/metadata flag. That version is "waiting for review" now, but I fear it will just be auto-rejected again because the app listing now has a spam flag on it. The app's first rejection came after a 5 min review (measured by the "in review" to "rejected" email timestamps), but each rejection review since then has been <60 seconds. Yesterday I tried calling App Review twice just to get more info, both times I waited on hold for 3 hours before the system transferred me to consumer support who of course coud not help or transfer me to anyone. I have also emailed App Review a few times, submitted an appeal, replied to App Review messages in App Store Connect seeking more information... nobody will tell me anything. Does anyone have any advice or ideas as to what I should change next? App Listing Info: TestFlight Link: https://testflight.apple.com/join/ZKQwDMN7 Promo Text: Rediscover your music. Explore your music library in new ways, with a built-in DJ, smart playlists, tuneable radio stations, comments, and much more. Keywords: apple music,player,library,playlists,smart playlist,radio,dj,discover,albums,artists,spotify,songs Description: Jelly Music gives your music library a fresh start. Built for Apple Music listeners who want more control over their collection, Jelly combines a beautiful music player with powerful library organization, smart discovery, personalized radio, and features designed to help you rediscover the music you already love. YOUR LIBRARY, REIMAGINED Browse your songs, albums, artists, playlists, genres, and more through a fast, thoughtfully designed interface. Jelly makes even large music libraries feel approachable again. SMART FILTERS & PLAYLISTS Find exactly what you want to hear. Create powerful filters using your music's metadata, organize your collection your way, and turn the results into playlists. REDISCOVER YOUR MUSIC Jelly helps surface music that's been hiding in your library — from forgotten favorites to albums and artists you haven't visited in years. JELLY DJ Start a personalized radio session built around your listening history, favorites, throwbacks, and discoveries. Let Jelly DJ guide the session, or mute the DJ and simply enjoy the mix. DISCOVER SOMETHING NEW Explore personalized recommendations, new releases, stations, music videos, and more without losing sight of the library you've spent years building. MADE FOR MUSIC NERDS Jelly includes the details and controls serious music-library users love, while keeping the experience simple enough for everyday listening. APPLE MUSIC, STILL YOUR MUSIC Jelly works alongside Apple Music rather than replacing your library. Sign in with your Apple Music account and explore your existing music through an entirely new experience. And with Jelly Music on Mac, you can take even greater control of your library and keep your Jelly experience in sync across devices. Jelly Music requires an Apple Music subscription for Apple Music catalog playback and certain features. Availability of Apple Music content and features may vary by region. Note on Pricing: a Paid Unlock (yearly or lifetime purchase) is required to use the Pro features of this app. This provides access and tailored experiences on iOS, iPadOS, and macOS. Terms and Conditions: [link] Privacy Policy: [link] Review Notes: To test this app, allow access to your Apple Music library and test Jelly Music as you would your typical music app. Play songs, skip/seek, modify queue, etc. See video overview explainer here: https://drive.google.com/file/d/1nI0BOuxWxpdNuFlvU3nkMo-3IIYiOkPl/view Jelly Music already has 100+ users on TestFlight and there are 100+ more users on the waiting list! People are excited for this new way to browse and manage their Apple Music library. Users can browse playlists/songs/artists/albums with numerous different view options on each screen. Get organized with playlist folders and smart playlists. Listen to DJ Radio which combines music from their library with other Apple Music they might like. Start radio stations from playlists or songs, with controls for how "exploratory" those stations should be. View and edit song metadata and comments/ratings right from their iPhone or iPad if they enable Mac Sync. Bump songs to the top of their library, while retaining the original date added. Control Sonos speakers right from Jelly. Style their experience with custom themes. And a lot more! Terms and Privacy links are listed in app description. Including below for reference: Terms and Conditions: xxx Privacy Policy: xxx In-App Purchases should be working. They work for me when testing with Xcode StoreKit and with my Apple Sandbox user. Purchases also work for TestFlight users. Please note, in-app purchases and downloadable Asset Packs are attached to this iOS version for review. The asset packs are for the dj voices, 1 pack per voice. Pro mode unlocks in-app extra features (folders, smart playlists, and mac sync) and does not relate to Apple Music content. If you have questions or concerns please feel free to call me at xxx App Store Screenshots: (Here are 3 of the 6 screenshots. They use fake artwork / metadata to avoid copyright issues)

I am having difficulty getting clarification from App Review regarding an external tip link and Guideline 3.1.1. My app is distributed exclusively on the United States App Store storefront. It is a free app, and the "About" page contains an optional “Buy Me a Coffee” link that opens an external browser. The tip does not unlock any content, functionality, subscription, service, or other benefit in the app. App Review has told me that the link must be replaced with In-App Purchase and cited the following language from Guideline 3.1.1: “We understand you have reviewed the updated App Review Guidelines and have questions regarding whether apps are still required to use in-app purchase to process "tips" for developers and digital content creators. Please note that the recent changes to guidelines 3.1.1, 3.1.1(a), 3.1.3 and 3.1.3(a) have not changed the scenarios where In-App Purchase is required. Guideline 3.1.1 states in part, "Apps may use in-app purchase currencies to enable customers to "tip" the developer or digital content providers in the app." To resolve the issues with your current submission, it would be appropriate to revise the app to use in-app purchase to process "tips" for developers and digital content creators. Please let us know if you have further questions. We look forward to reviewing the app once the appropriate changes have been made.” I am having difficulty reconciling that interpretation with the current language of Guideline 3.1.1(a), which specifically states that entitlements are not required for buttons, external links, or other calls to action in United States storefront apps. Apple’s May 1, 2025 guideline update also states that Guidelines 3.1.1, 3.1.1(a), 3.1.3, and 3.1.3(a) were changed in response to the U.S. court decision concerning external purchasing links. The 3.1.1 language regarding tips says that apps “may use” IAP for tips; it does not appear to state that an optional tip that provides no digital goods, services, or functionality must use IAP. Has anyone recently dealt with this specific situation for a U.S.-storefront-only app? If so, was an App Review Board appeal required to resolve it? I am trying to determine whether I am overlooking another provision of the guidelines that specifically requires an optional external tip to use IAP in a United States storefront app. I have a pending appeal but am frankly disappointed in this situation and I do not want to wait weeks or months to get this through the appeal process.

Hello, My app has been in “Waiting for Review” status since August 22, 2026. It has now been 7 days, and the review has not started yet. I understand that App Review times can vary, but I would like to know whether there is currently a general delay with App Review. Has anyone else submitted an app around August 20–23 and is still waiting for the review to begin? Developer ID for reference: 87f4555e-11e0-4be6-8e84-12b9400e4fa0 Any information about current App Review delays or expected waiting times would be greatly appreciated. Thank you!

Hello everyone, We are reaching out here because we honestly don’t know what else to do. Our Apple Developer account was restricted and our application disappeared from the App Store. We immediately contacted Apple and opened a case: Case ID: 20000149095871 It has now been one full week, and unfortunately, we have not received any response or explanation from Apple. We are completely confused and extremely concerned because we still do not understand what caused this action or what we are supposed to do to resolve it. We have spent almost three years developing this product. Our service helps people meet, build relationships, and create families. We have always treated Apple and the App Store Review process with great respect. Whenever Apple raised concerns in the past, we communicated openly with App Review, including by phone, and made every change that was requested from us. We are ready to cooperate fully, provide any information or documentation required, make any necessary changes, or speak directly with the appropriate Apple team. We are not asking for special treatment or for Apple to ignore any rules. We are simply asking for someone to review our case, explain what happened, and give us an opportunity to resolve the situation. A week without any response has left us at a complete loss. If anyone from Apple sees this, or if anyone in the developer community knows a legitimate way to escalate this case, we would be incredibly grateful for your help. Thank you.

Hello, I am investigating an intermittent In-App Purchase failure that occurred during App Review for the first release of my app. Environment Review device: iPad Air 11-inch (M3) OS: iPadOS 26.6 Environment: App Review sandbox Product type: Consumable StoreKit integration: RevenueCat through react-native-purchases 10.4.3 Observed behavior StoreKit successfully returned the products, localized names, and prices. The reviewer could see the credit packs and initiate the native purchase flow. My diagnostics show this sequence: Purchase initiated PURCHASE_CANCELLED; no transaction evidence Purchase initiated again RevenueCat code 2: STORE_PROBLEM elapsed: 9.4 seconds no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE no transaction evidence Purchase initiated again RevenueCat code 5: PRODUCT_NOT_AVAILABLE_FOR_PURCHASE elapsed: 0.6 seconds no transaction evidence code-block The relevant sanitized logs are: { "occurredAt": "2026-08-25T12:52:59.733Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "2", "providerReadableCode": "STORE_PROBLEM", "transactionEvidence": false, "elapsedMs": 9417 } code-block { "occurredAt": "2026-08-25T12:55:42.752Z", "platform": "ios", "appVersion": "1.0.0", "build": "14", "productId": "HIDDEN_FOR_DISPLAY", "stage": "STORE_CHECKOUT", "providerCode": "5", "providerReadableCode": "PRODUCT_NOT_AVAILABLE_FOR_PURCHASE", "transactionEvidence": false, "elapsedMs": 637 } code-block No App Store transaction was created, and therefore RevenueCat received no transaction or webhook for these attempts. Configuration verified I confirmed that: The affected product and the other consumable products are attached to the App Review submission. Product IDs match between the app, App Store Connect, and RevenueCat. Prices and localizations are configured. The products are available in the relevant storefronts. The Paid Apps Agreement is active. Banking and tax information are active. The In-App Purchase capability is present. The distribution build does not use a local StoreKit configuration file. The same build and affected product completed successfully afterward on a physical device using Apple Sandbox. The native purchase sheet opened, the transaction completed, and the consumable content was delivered successfully in my reproduction. The product metadata clearly remained available because its localized name and price were displayed. However, after the initial STORE_PROBLEM, subsequent purchase requests were rejected almost immediately as PRODUCT_NOT_AVAILABLE_FOR_PURCHASE. I do not have the underlying Apple NSError, such as an ASDServerErrorDomain or AMSErrorDomain value, because it was not exposed in my remote diagnostic record. Questions Can a failed sandbox transaction leave the StoreKit account/session or commerce-catalog state temporarily inconsistent, causing subsequent requests for an otherwise loaded product to return storeProductNotAvailable? Does StoreKit use separate metadata and transaction-eligibility services, allowing product information to load while the same product is rejected during purchase()? Are there known sandbox or StoreKit issues on iPadOS 26.6 that could produce this sequence? Could a stale App Review sandbox account token or storefront session explain the transition from STORE_PROBLEM to PRODUCT_NOT_AVAILABLE_FOR_PURCHASE? Is there any developer-side configuration that could explain this when the same product and binary complete successfully using another sandbox session? What additional logging should I capture from RevenueCat’s React Native SDK to preserve the complete underlying Apple error chain?

Hi. Hoping a human can take a look at this one. I made an app for Echo Park Rising, a free community music festival in Los Angeles that starts today, August 29. The app holds the schedule, the venue map, and the set times. The whole idea is that someone can wander into the neighborhood, open it, and figure out which stage to walk to next. The festival is free and so is the app. Nothing is sold in the app and there are no paid ads. Apple ID: 6805272281 Submission ID: 6292ee8e-4027-46cd-8c50-4688d9352903 Version 1.0.1 (8), submitted August 26 at 9:47 PM Pacific Status: Waiting for Review I understand new apps can take longer and I know the queue has been rough this year. For what it's worth, this should be a quick one. There are no accounts or logins, no user generated content, and no tracking. Nothing the app collects is linked to your identity. The TestFlight build was approved almost immediately. I filed an expedited review request earlier this week and mentioned the festival dates, but I am not sure if it went through correctly. My support cases (20000150506461 and 20000150362000) are still unanswered, and phone support opens back up Monday. The festival will be over by then. Hoping for a miracle here. People are going to be walking around the neighborhood all weekend, and I built this with love so they could find their way from stage to stage. This is my favorite neighborhood event of the year. Could someone take a look at the submission today, or at least tell me whether the expedite was applied? I would be very grateful. Thank you for reading.

Hello Apple Developer Support, I am requesting assistance regarding the App Review rejection of my application, My Majikan. App Name: My Majikan Apple ID: 6803704433 Version: 1.5 Bundle ID: mymajikan.MyMajikan Submission ID: 9e81e141-e752-4413-8134-6e2054f36bd3 Rejection: Guideline 4.3(a) – Design – Spam The review message states that the application may share a similar binary, metadata, assets, or concept with applications submitted by other developers. However, the message does not identify which element or application caused the similarity concern. My Majikan is an integrated workforce management platform developed for Malaysian employers and employees. It connects to our own backend and includes role-based Employer and Employee portals, GPS attendance, work schedules, leave and overtime management, expense claims, payroll, electronic payslips, company announcements, internal chat, and audio/video workplace calling. This is a single application with one Bundle ID. We are not submitting separate reskinned versions for different companies. Could you please help clarify whether the rejection relates to: Source code or binary similarity Application design or assets App Store metadata The application’s general concept Another specific application We would appreciate more specific information so we can address the concern accurately. We can provide source-code ownership evidence, backend and domain ownership, company information, reviewer credentials, and a screen recording demonstrating the complete application workflow. Thank you for your assistance. Kind regards,

Hello Apple App Review Team, We are urgently seeking assistance regarding our Apple Developer account. Our application was successfully reviewed and approved by Apple on August 23. Shortly afterward, however, the application unexpectedly became unavailable on the App Store, and access to important sections of App Store Connect, including Distribution and TestFlight, disappeared. We have not received a clear explanation of what caused this restriction. We immediately contacted Apple and opened Case ID 20000149095871, but more than 72 hours have now passed without a response or any information about the status of the case. We fully respect the App Store Review Guidelines and have always cooperated with the App Review team. In the past, when reviewers raised concerns, we communicated directly with App Review, clarified how our application works, and promptly made any requested changes. If there is currently an issue with our application or developer account, we are completely ready to cooperate, provide any information required, make any necessary corrections, or speak with the App Review team by phone. This situation is having a serious impact on our business and our users, while we currently have no information about what happened or what action is required from us. Could an Apple App Review staff member please check Case ID 20000149095871 and advise whether the case can be reviewed or escalated to the appropriate team? We would greatly appreciate any assistance. Thank you.

App stuck in "Waiting for Review" for 3 days — anyone else? My app has been sitting in "Waiting for Review" status for 3 days now with no update. No rejection, no request for more info, nothing. Has anyone else run into this recently? Just trying to figure out if this is a known delay right now or something specific to my submission.